Skip to content

Conversation

@felser
Copy link
Contributor

@felser felser commented Jul 24, 2020

When manually flashing an application binary to the MULTITECH drive, a FAIL.TXT
file is produced with the following info:
“The application file format is unknown and cannot be parsed and/or processed”.

Summary of changes

Removed ROM and RAM definitions for target MTS_DRAGONFLY_F413RH in targets.json.

Impact of changes

Migration actions required

Documentation

None


Pull request type

[X] Patch update (Bug fix / Target update / Docs update / Test update / Refactor)
[] Feature update (New feature / Functionality change / New API)
[] Major update (Breaking change E.g. Return code change / API behaviour change)

Test results

[] No Tests required for this change (E.g docs only update)
[] Covered by existing mbed-os tests (Greentea or Unittest)
[X] Tests / results supplied as part of this PR

Built blinky. Drag and drop works with all bin files produced and the application blinks the LED as expected.
Tested with and without a bootloader.

Reviewers


When manually flashing an application binary to the MULTITECH drive, a FAIL.TXT
file is produced with the following info:
“The application file format is unknown and cannot be parsed and/or processed”.
@ciarmcom ciarmcom added the release-type: patch Indentifies a PR as containing just a patch label Jul 24, 2020
@ciarmcom
Copy link
Member

@felser, thank you for your changes.
@ARMmbed/mbed-os-maintainers please review.

@ciarmcom ciarmcom requested a review from a team July 24, 2020 21:00
Copy link
Contributor

@0xc0170 0xc0170 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How is this fixing the problem? If you do not provide these sizes, they come from packs (there are different values?) ?

@felser
Copy link
Contributor Author

felser commented Jul 27, 2020

The problem is specifically with the definition "mbed_ram_start": "0x200001D8". It should be "mbed_ram_start": "0x20000000". It seems redundant to define these in targets.json as they are defined for "STM32F413xH". That's how the other STM32F413 platforms are configured. Specifically the Disco and Nucleo 413ZH platforms which have the same memory layout as the 413RH.

@mergify mergify bot added needs: CI and removed needs: review labels Jul 29, 2020
@0xc0170
Copy link
Contributor

0xc0170 commented Jul 29, 2020

CI started

@mbed-ci
Copy link

mbed-ci commented Jul 29, 2020

Test run: SUCCESS

Summary: 6 of 6 test jobs passed
Build number : 1
Build artifacts

@0xc0170 0xc0170 merged commit 821631a into ARMmbed:master Jul 30, 2020
@mergify mergify bot removed the ready for merge label Jul 30, 2020
@mbedmain mbedmain added release-version: 6.2.1 Release-pending and removed release-type: patch Indentifies a PR as containing just a patch Release-pending labels Aug 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants